Method and apparatus for implementing dual connectivity

ABSTRACT

A wireless access node (e.g. a master eNB (MeNB)) is described for a wireless communication system that comprises a first wireless access network and a second wireless access network supporting a dual connectivity terminal device arranged to communicate with both the wireless access node (MeNB) on the first wireless access network and a second wireless access node (e.g. a secondary eNB (SeNB)) on the second wireless access network is provided. The wireless access node comprises a communication unit and a controller. The controller is operably coupled to the communication unit and configured to control the communication unit to transmit a first message including configuration information for a secondary cell group (SCG) to perform a certain action, to the other base station, and to receive a second message in response to the first message from the other base station, and to control the communication to transmit a third message based on the second message to the terminal, wherein the configuration information includes multimedia broadcast multicast service (MBMS) interest information.

CROSS-REFERENCE TO RELATED APPLICATION(S) AND CLAIM OF PRIORITY

The present application is related to and claims priority from and thebenefit under 35 U.S.C. § 119(a) of British Patent Application No.1401737.0, filed on Jan. 31, 2014, which is hereby incorporated byreference for all purposes as if fully set forth herein.

TECHNICAL FIELD

This invention relates generally to implementing dual connectivitydevices in a communications system, and in particular, but not limitedto, supporting dual connectivity user equipment being concurrentlyconnected to a master eNodeB and a secondary eNodeB, each of whichcontrol one or multiple cells, such as macro cell(s) and small cell(s).

BACKGROUND

A recent development in third generation (3G) wireless communications isthe long term evolution (LTE) cellular communication standard, sometimesreferred to as 4th generation (4G) wireless communications. Both 3G and4G technologies are compliant with third generation partnership project(3GPP™) standards.

SUMMARY

According to an aspect of the present invention, a method in a wirelesscommunication system supporting a dual connectivity, the methodcomprising: transmitting, by a base station, a first message includingconfiguration information for a secondary cell group (SCG) to perform acertain action, to other base station; receiving, by the base station, asecond message in response to the first message from the other basestation; and transmitting, by the base station, a third message based onthe second message to a terminal, wherein the configuration informationincludes multimedia broadcast multicast service (MBMS) interestinformation.

According to another aspect of the present invention, a method in awireless communication system supporting a dual connectivity, the methodcomprising: receiving, by a base station, a first message includingconfiguration information for a secondary cell group (SCG) to perform acertain action, from other base station; and transmitting, by the basestation, a second message in response to the first message to the otherbase station, wherein the configuration information includes multimediabroadcast multicast service (MBMS) interest information.

According to another aspect of the present invention, a base station ina wireless communication system supporting a dual connectivity, the basestation comprising: a communication unit configured to transmit and toreceive a signal to and from other base station and a terminal; and acontroller configured to control the communication unit to transmit afirst message including configuration information for a secondary cellgroup (SCG) to perform a certain action, to the other base station, andto receive a second message in response to the first message from theother base station, and to control the communication to transmit a thirdmessage based on the second message to the terminal, wherein theconfiguration information includes multimedia broadcast multicastservice (MBMS) interest information.

According to another aspect of the present invention, a base station ina wireless communication system supporting a dual connectivity, the basestation comprising: a communication unit configured to transmit and toreceive a signal to and from other base station and a terminal; and acontroller configured to control the communication to receive a firstmessage including configuration information for a secondary cell group(SCG) to perform a certain action, from other base station, and totransmit a second message in response to the first message to the otherbase station, wherein the configuration information includes multimediabroadcast multicast service (MBMS) interest information.

Before undertaking the DETAILED DESCRIPTION below, it is advantageous toset forth definitions of certain words and phrases used throughout thispatent document: the terms “include” and “comprise,” as well asderivatives thereof, mean inclusion without limitation; the term “or,”is inclusive, meaning and or; the phrases “associated with” and“associated therewith,” as well as derivatives thereof, mean to include,be included within, interconnect with, contain, be contained within,connect to or with, couple to or with, be communicable with, cooperatewith, interleave, juxtapose, be proximate to, be bound to or with, have,have a property of, or the like; and the term “controller” means anydevice, system or part thereof that controls at least one operation,such a device is implemented in hardware, firmware or software, or somecombination of at least two of the same. It should be noted that thefunctionality associated with any particular controller is centralizedor distributed, whether locally or remotely. Definitions for certainwords and phrases are provided throughout this patent document, those ofordinary skill in the art should understand that in many, if not mostinstances, such definitions apply to prior, as well as future uses ofsuch defined words and phrases.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and itsadvantages, reference is now made to the following description taken inconjunction with the accompanying drawings, in which like referencenumerals represent like parts: this disclosure

FIG. 1 illustrates an example simplified architecture diagram supportinga dual connectivity UE according to this disclosure;

FIG. 2 illustrates an example 3GPP™ LTE cellular communication systemadapted according to this disclosure;

FIG. 3 illustrates a block diagram of example wireless communicationunits according to this disclosure;

FIG. 4 illustrates an example simplified message sequence chart for UEstatus forwarding according to this disclosure;

FIG. 5 illustrates an example simplified message sequence chart for asecondary cell addition or modification procedure according to thisdisclosure;

FIG. 6 illustrates a block diagram of example wireless communicationunits according to this disclosure;

FIG. 7 illustrates an example of uplink data in a PCell and pSCellaccording to this disclosure;

FIG. 8 illustrates an example simplified high level message sequencechart for providing uplink SPS activation according to this disclosure;

FIG. 9 illustrates an example simplified high level message sequencechart for providing UE status information according to this disclosure;

FIG. 10 illustrates an example activation or deactivation MAC controlelement according to this disclosure;

FIG. 11 illustrates an example message sequence chart for a dualconnectivity UE operation according to this disclosure; and

FIG. 12 illustrates an example message sequence chart for SPS activationof a dual connectivity UE according to this disclosure.

Skilled artisans will appreciate that elements in the figures areillustrated for simplicity and clarity and have not necessarily beendrawn to scale. For example, the dimensions or relative positioning ofsome of the elements in the figures are exaggerated relative to otherelements to help to improve understanding of various embodiments of thepresent invention. Also, common but well-understood elements that areuseful or necessary in a commercially feasible embodiment are often notdepicted in order to facilitate a less obstructed view of these variousembodiments of the present invention. It will be further appreciatedthat certain actions or steps are described or depicted in a particularorder of occurrence while those skilled in the art will understand thatsuch specificity with respect to sequence is not actually required. Itwill also be understood that the terms and expressions used herein havethe ordinary technical meaning as is accorded to such terms andexpressions by persons skilled in the technical field as set forth aboveexcept where different specific meanings have otherwise been set forthherein.

DETAILED DESCRIPTION

FIGS. 1 through 12, discussed below, and the various embodiments used todescribe the principles of the present disclosure in this patentdocument are by way of illustration only and should not be construed inany way to limit the scope of the disclosure. Those skilled in the artwill understand that the principles of the present disclosure areimplemented in any suitably arranged communication system and electronicdevice. Although example embodiments of this disclosure are describedwith reference to dual connectivity UEs, it is envisaged that someaspects of this disclosure are not so constrained or limited. Exampleembodiments are described with reference to radio access networks, whichterm encompasses and is considered to be equivalent to andinterchangeable with communication cells, namely the facilitation ofcommunications within a cell that accesses other parts of thecommunication system as a whole.

Increasing the number of network nodes, and thereby situating themphysically closer to user terminals, is one important and usefulmechanism to improve traffic capacity and extending achievable user datarates of a wireless communications system. In cellular systems, networkdensification is achieved by deployment of complementary low-power nodesunder the coverage of an existing cellular macro-node layer. In such adeployment, the low power nodes provide very high traffic capacity andvery high user throughput locally, for example in indoor and outdoorhotspot positions.

Some Standard activities have focused on ensuring a high degree ofinterworking between the macro and low power layers, including differentforms of macro assistance to the low-power layer as well as dual layerconnectivity. Dual connectivity refers to an operation of a userequipment (UE) that is able to consume radio resources provided by atleast two different network points, such as a macro-node and a low-powernode, connected via a non-ideal backhaul. With existing carrieraggregation (CA) in LTE, all serving cells the UE is configured with arecontrolled by one eNB. In case of dual connectivity, some of the UE'sserving cells are controlled by one eNB while others are controlled byanother eNB, the respective control being handled by either a macro-celleNodeB (eNB) or a small cell eNB (each of which could control macro andsmall cells). The communications in each cell to or from UEs typicallyare supported by a respective base station, referred to as evolved NodeB(eNB), with one eNB supporting communications to or from each cell. Ifthe UE is a dual connectivity UE, its communications to or from the eNBsometimes differ, such as one eNB (Master eNB) is overall responsiblefor the controlling the radio connection of the UE whilst the one ormore other eNBs (Secondary eNBs) are merely involved in providingadditional radio resources.

Referring to FIG. 1, a known simplified architecture diagram 100illustrates dual connectivity for a wireless subscriber unit, sometimesreferred to as a terminal device, such as a UE according to thisdisclosure. The known simplified architecture diagram 100 comprises amacro cell eNB 101, a small cell eNB (sometimes referred to as an accesspoint) 103, and a dual connectivity UE 105. The macro cell eNB 101 isconnected to the small cell eNB 103, both being engaged in dualconnectivity, via a non-ideal backhaul 107, generally an X2 (based onX2) interface that specifies some additional procedures for coordinatingaspects relevant for dual connectivity. Macro cell eNB 101 supportscommunications over a coverage area 109, sometimes referred to as acell, which encompasses the dual connectivity UE 105 and at least aportion of a small cell coverage area 111. The dual connectivity UE 105is configured with a serving cell 109 at carrier frequency F1 113 frommacro cell eNB 101 and a serving cell 111 at carrier frequency F2 115small cell eNB 103, which in this case are at different frequencies.

Dual connectivity operation only applies in radio resource control (RRC)state RRC_CONNECTED. Furthermore, the Radio Resource Control signalingis exchanged between the dual connectivity UE and the MeNB, althoughpart of the configuration information originate from the SeNB. Accordingto current RRC specifications, the dual connectivity UE 105 isconfigured to provide information to assist the network in which itresides. This information includes, amongst other things, UE statusinformation, comprising power preference indication (PPI), which is anindication as to whether the dual connectivity UE 105 prefers powersaving, a proximity indication as to whether the dual connectivity UE105 is in proximity to a closed subscriber group (CSG) cell, indicationsof having radio link failure (RLF) information, connection establishmentfailure (CEF) information or minimization of drive test informationavailable, information to assist the network to avoid in devicecoexistence (IDC) and multimedia broadcast multicast service (MBMS)interest information, which indicates whether a dual connectivity UE 105is interested to receive MBMS via a multicast radio bearer (MRB) on aparticular frequency. Notably, this information is currently notavailable to SeNB, whereas access to this information could be verybeneficial to the SeNB.

In the case of dual connectivity UEs, the macro cell eNB 101 and smallcell eNB 103 each comprise their own independent scheduler, required tooptimize the use of varying radio conditions. Thus, a situation arisewhere there are two eNBs, both independently dynamically schedule ULtransmissions for the dual connectivity UE, whilst they have to sharethe UL power that the dual connectivity UE use for these transmissions.If, for the same moment in time (such as a subfame), both eNBs allocatea large grant to the dual connectivity UE, the dual connectivity UE haveinsufficient power to handle this and will have to scale the power ofthe different transmissions. In such a case the time or frequencyresources will not be used optimally from a network capacityperspective.

Currently, in order to avoid this power limited mode of operation, theevolved-universal mobile telecommunication system terrestrial radioaccess network (E-UTRAN) configure the UE to provide assistanceinformation to avoid this uplink power limitation such as by configuringPower HeadRoom (PHR) reporting. UEs in this situation are generallyconfigured to send PHR concerning each serving cell, which includes areport detailing an amount of spare power that would still be available(assuming that all available UE power would be used for a physicaluplink shared channel (PUSCH) transmission in the concerned cell. Ifthere is no PUSCH transmission, the UE assumes a transport block of areference size, while for the PCell the UE provides a separate reportfor the physical uplink control channel (PUCCH). Based on the PHRreport, the eNB estimate whether the UE was power limited, in whichcase, it would have utilized power scaling. The eNB generally utilizesthis information when granting resources to the UE for future uplinktransmissions.

A dual connectivity UE, such as UE 105, is assumed to provide a PHRreport to each eNB. However, it is not clear from the current Standardsdocuments what information the dual connectivity UE 105 should includein the PHR reports for the macro cell eNB 101 and the small cell eNB103. It has been proposed that current dual connectivity UEs 105 arerequired to provide a PHR report concerning all cells to each eNB 101,103 such as MeNB would receive PHR concerning cells in the secondarycell group. With such an approach, it is possible for each eNB 101, 103to obtain a complete picture of the transmission power usage of relevantdual connectivity UEs, and therefore estimate whether dual connectivityUEs were power limited and utilized power scaling. A problem with theabove mentioned approach is that PHR reports generated when a relevantdual connectivity UE is power limited, not necessarily be relevant inthe near future, as the uplink (UL) power limitation status changerapidly with varying uplink data rates and radio link quality.

Example embodiments of this disclosure are described with reference toproviding dual connectivity terminal UE status information, notablyreferring to status information that relates to the specific dualconnectivity UEs in the described implementation, rather than imply thatthe information is solely specific to dual connectivity UEs, as thisinformation itself has no specific relevance to the concept of dualconnectivity. Thus, the status information is used to make the SeNBaware of the UE status, where the UE is configured as a dualconnectivity UE.

Furthermore, the inventors have recognized and appreciated that two eNBsconcurrently communicating with a dual connectivity UE 105 each grant ULresources in which the UE transmits simultaneously. In such a scenario,the UE may well not have the transmit power required power to performthese simultaneous transmissions. In one example, this problem is solvedby enhancement of the power headroom (PHR) reporting. In anotherexample, the MeNB provides an indication to the SeNB informationregarding persistent or periodic UL transmissions that it has assignedto the UE.

Thus, example embodiments of this disclosure are also described withreference to provision of semi-persistent scheduling (SPS) activationsuch as a master eNB is aware of the SPS, and example embodimentspropose a mechanism to make the SeNB aware also. As such, variousexamples are described that concern transfer of information concerninglegacy functions, towards a dual connectivity specific node, such as asecondary eNB (SeNB).

Referring now to FIG. 2, part of a wireless communication system 200 isshown in outline, in accordance with one example embodiment of thisdisclosure. In this example embodiment, the wireless communicationsystem 200 is compliant with, and contains network elements capable ofoperating over, an Evolved-UMTS Terrestrial Radio Access Network(E-UTRAN) wireless communication system, which is currently underdiscussion in the third Generation Partnership Project (3GPP™)specification for long term evolution (LTE), based around OrthogonalFrequency Division Multiple Access (OFDMA) in the downlink (DL) andSingle Carrier Frequency Division Multiple Access (SC-FDMA) in theuplink (UL), as described in the 3GPP™ TS 36.xxx series ofspecifications. Within LTE, both time division duplex (TDD) andfrequency division duplex (FDD) modes are defined.

The part of the wireless communication system 200 architecture comprisesat least two eNodeBs (evolved NodeBs) 210, 203 which perform manystandard base station functions. A wireless communication system willtypically have a large number of such infrastructure elements where, forclarity purposes, only a limited number are shown in FIG. 2.

In this example, there is a first eNB 210, denoted master MeNB, and asecond eNB 203, denoted secondary SeNB operably coupled to each othervia an X2 interface. MeNB 210 is denoted as the master eNB with respectto dual connectivity UE 225, as it currently is served by MeNB 210,whereas second eNB 203 is denoted as the SeNB with respect to dualconnectivity UE 225, as it may not be the primary eNB serving dualconnectivity UE 225. In some other examples, eNB 203 is a master MeNBfor some UEs and a secondary SeNB for other UEs. Similarly, eNB 210 is asecondary SeNB for some UEs and a master MeNB for other UEs.

FIG. 2 illustrates two groups of serving cells configured for UE 225such as a first cell group 207 associated with the (first) MeNB 210,denoted a master cell group (MCG), and a second cell group 209associated with the (second) SeNB 203, denoted a secondary cell group(SCG). The MCG includes one cell providing some specific functionality:the primary Cell (PCell). Likewise, the SCG includes a cell withspecific but different functionality: the primary Secondary Cell(PSCell). All other serving cells are referred to as Secondary Cells(SCells).

In some examples, the first cell group 207 comprises a number of macrocells, a number of small cells or a mixture of both (or any other celltype) 211. The second cell group 209 also comprises a number of macrocells, a number of small cells or a mixture of both (or any other celltype) 213. Further, there are some further cell groups that are notcurrently available to dual connectivity UE 225, denoted as 215.

Generally, the dual connectivity UE 225 is agnostic of the nodecontrolling a particular cell. Each UE 225 comprises at least atransceiver unit 227 (such as a communication unit) operably coupled tosignal processing logic 258 (such as controller) (with one UEillustrated in such detail for clarity purposes only). The wirelesscommunication system comprises many other UEs 225 and eNBs 210, 203,providing multiple opportunities for wireless communication unitsaccessing the communication system via radio access networks and radioaccess nodes, which for clarity purposes are not shown.

In some examples, two wireless access nodes, such as MeNB 210 and SeNB203 are operably coupled to a dual connectivity UE 225. The firstwireless access node is deemed a master eNB (MeNB). In some examples,the MeNB 210 is used to provide solid connectivity with robust mobilityperformance by use of macro-cells for the dual connectivity UE 225 witha core network (not shown), whereas the SeNB 203 is arranged to provideadditional radio resources for the dual connectivity UE 225.

Thus, in other examples, it is envisaged that the MeNB and SeNB isinterchanged. In some examples, it is envisaged that the MeNB supportcommunications by one or more macro cells and the SeNB supportcommunications by one or more small cells. In other examples, it isenvisaged that the MeNB and SeNB support communications in the same orsimilar cell size, such as both support communications by one or moremacro cells or both support communications by one or more small cells.Further, in some examples, it is envisaged that an eNB (either MeNB orSeNB) control both macro and small cells; or an eNB function as a MeNBfor one UE and the same eNB function as a SeNB for another UE, such aswhether an eNB is an MeNB or an SeNB for a particular UE is dependent onthe role or functionality performed by the eNB.

In some examples, the MeNB 210 is arranged to transmit 223 a full or asubset of UE status information to one or more SeNB 203. This comprise,for example, one or more of in device coexistence (IDC) information,required for problems requiring time division multiplexing (TDM)solutions and PPI, for configuring discontinuous reception (DRX) states.In some examples, the subset of UE status information sent to an SeNBmay not comprise multimedia broadcast multicast service (MBMS) interestinformation, or proximity information. Therefore, in some examples, ifone or more SeNB(s) 203 connects with a dual connectivity UE 225, theMeNB 210 forwards UE status information to the SeNB(s) 203. Further, theUE status information that is forwarded is a subset of UE statusinformation received by the MeNB 210.

In some examples, MeNB 210 is arranged to initiate forwarding of UEstatus information when establishing a secondary cell group (SCG) 209,such as a group of cells that the UE is configured with that arecontrolled by the SeNB 210. Alternatively, or additionally, MeNB 210forwards a change of UE status information as and when such a changeoccurs. Further, in some examples, the MeNB 210 only forwards initial UEstatus information if it is deemed essential, useful or beneficial forthe one or more SeNB 203 to support communications with the dualconnectivity UE, for example if the UE status information comprises IDCinformation required for TDM solutions.

Further, in some examples, the MeNB 210 is arranged to initiateforwarding of UE status information, or a subset thereof, if the MeNB(s)210 receives (changed) UE status information. Therefore, in someexamples, MeNB 210 is arranged to forward UE status information to theSeNB 203 when the MeNB 210 receives updated status information from dualconnectivity UE 225. Further, in some examples, the MeNB 210 is arrangedto only forward up-dated UE status information, or a subset thereof, ifit is the updated information is deemed essential or beneficial for theconcerned SeNB.

In some examples, a source MeNB is arranged to, during a handoveroperation involving change of MeNB, forward UE status information, or asubset thereof, to one or more target MeNBs. Therefore, upon handover, asource MeNB forwards UE status information to a target (new) MeNB,whilst the UE repeats the UE status provided less than one secondpreceding receipt of a handover command, for example upon handover thereare two options: a) the UE repeats the status information, or b) thesource MeNB, for example MeNB, transfers the status information to thetarget MeNB, and the UE only repeats in case there was a late changethat has arrived too late at the source MeNB to be forwarded (such asthe one second window).

In some examples, due to these procedures for transfer of statusinformation upon change of MeNB, the target MeNB obtains up-to-date UEstatus information. However, the target MeNB can be unable to detectwhether or not the UE status information changed upon change of MeNB.Thus, in case the SeNB remains the same upon change of MeNB, the targetMeNB is arranged to transfer the updated UE status information to theSeNB, provided that it is deemed essential or beneficial for theconcerned SeNB. Correspondingly, in some examples, the SeNB should clearthe UE status information upon change of MeNB. In some examples,forwarding of UE status information, for example relating to proximity,failure and logged measurement information, may not occur. Instead, theUE repeats transmissions relating to proximity, failure and loggedmeasurement information, for example, following a handover, to thetarget MeNodeB.

In some examples, MeNB 210 is operable to determine the functionality ofone or more SeNB(s) 203, allowing MeNB 210 to determine whether receiveddata is relevant or beneficial for the one or more SeNB(s) 203. In someexamples, MeNB 210 considers MBMS and proximity information to benon-essential or non-beneficial for a particular one or more SeNB(s) 203and, therefore, determine not to forward this information onto theparticular one or more SeNB(s) 203 if they do not support thisfunctionality. Further, in some examples, MeNB 210 considers that IDCstatus information is not essential or not beneficial for a particularone or more SeNB(s) 203 if, for example, the one or more SeNB(s) 203 donot support the relevant functionality, or the IDC status informationdoes not include assistance information related to a time divisionmultiplex (TDM) solution or only includes assistance informationconcerning frequencies not supported by the SeNB(s) 203. Furthermore, insome examples, MeNB 210 considers that IDC information is not essentialor not beneficial for a particular one or more SeNB(s) 203 if it onlyconcerns IDC status information affecting frequency divisionmultiplexing (FDM) solutions. This is due to FDM solutions beingcontrolled by the MeNB 210.

In some examples, the MeNB 210 determines whether to forward a full setof UE status information to one or more SeNB(s) 203, or a subset of UEstatus information. Therefore, in some examples, the MeNB 210 determinesthat only a subset of UE status information that is essential orbeneficial for one or more SeNB(s) 203 should be forwarded. In somefurther examples, a determined subset of UE status information mayalways be provided to one or more relevant SeNB(s) 203. In some otherexamples, the determined subset of UE status information can onlycomprise information parameters that have changed from the last timethey were signaled to one or more SeNB(s) 203, generally referred to asdelta signaling.

In some examples, it is generally assumed that for a UE configured withdual connectivity, the MeNB handles the configuration of measurementsand the related gaps in transmissions. In some examples, the dualconnectivity UE provides IDC indications for frequencies for which, say,a measurement object is configured. For these, the dual connectivity UEindicates the affected frequencies (also indicating the direction of IDCinterference) and it also provides TDM information, such as either adiscontinuous receive (DRX) pattern or a pattern comprising one or moresubframe patterns.

Referring now to FIG. 3, block diagrams of wireless communicationsunits, for example MeNB 210, and SeNB(s) 203, adapted in accordance withsome example embodiments of this disclosure are shown. The wirelesscommunication units 210, 203 contain an antenna 302, for receivingtransmissions, coupled to an antenna switch or duplexer 304 thatprovides isolation between receive and transmit chains within thewireless communication units 210, 203. One or more receiver chains, asknown in the art, include receiver front-end circuitry 306 (effectivelyproviding reception, filtering and intermediate or base-band frequencyconversion). The receiver front-end circuitry 306 is coupled to a signalprocessing module 308 (generally realized by a digital signal processor(DSP)). A skilled artisan will appreciate that the level of integrationof receiver circuits or components is, in some instances,implementation-dependent.

The controller 314 maintains overall operational control of the wirelesscommunication units 210, 203. The controller 314 is also coupled to thereceiver front-end circuitry 306 and the signal processing module 308.In some examples, the controller 314 is also coupled to a buffer module317 and a memory device 316 that selectively stores operating regimes,such as decoding or encoding functions, synchronization patterns, codesequences, and the like. A timer 318 is operably coupled to thecontroller 314 to control the timing of operations (such as transmissionor reception of time-dependent signals) within the wirelesscommunication units 210, 203. As regards the transmit chain, thisessentially includes an input module 320, coupled in series throughtransmitter or modulation circuitry 322 and a power amplifier 324 to theantenna 302, antenna array, or plurality of antennas. The transmitter ormodulation circuitry 322 and the power amplifier 324 are operationallyresponsive to the controller 314.

The signal processor module 308 in the transmit chain is implemented asdistinct from the signal processor in the receive chain. Alternatively,a single processor is used to implement a processing of both transmitand receive signals, as shown in FIG. 3. Clearly, the various componentswithin the MeNB 210, SeNB 203 is realized in discrete or integratedcomponent form, with an ultimate structure therefore being anapplication-specific or design selection. In some examples, MeNB 210receives communications 221 from one or more dual connectivity UEs 225,wherein the communications 221 comprises status information relating tothe one or more dual connectivity UEs 225. In response to thisinformation, the MeNB 210 signals, via 223, a message to SeNB 203comprising the full status information received from the one or more UEs225, or a subset of information to the SeNB 203.

In response to the message 223 from the MeNB 210, the SeNB 203configures itself to communicate with the one or more dual connectivityUEs 225 via communications 222. In some examples, the controller 314 ofthe eNB 210 is operable to determine the functionality or capability ofthe SeNB 203. Therefore, in response thereto, the controller 314 isoperable to determine what dual connectivity UE 225 status informationis relevant or beneficial for the SeNB 203 based on its functionality orcapability, and subsequently transmit the full status information or asubset of the status information based on the determination.

Thus, in some examples, a wireless access node (such as a master eNB(MeNB)) 210 is described for a wireless communication system thatcomprises a first wireless access network and a second wireless accessnetwork supporting a dual connectivity terminal device. In someexamples, the UE is configured with (carrier aggregation (CA)) cellgroups such as a master cell group (MCG) and a secondary cell group(SCG), where each cell group is controlled by a different eNB. In someexamples, additionally or alternatively, the UE is considered as beingarranged to communicate with both the wireless access node (MeNB) 210 onthe first wireless access network and a second wireless access node(such as a secondary eNB 203 (SeNB)) on the second wireless accessnetwork. The wireless access node comprises: a transceiver (such as acommunication unit), a processor 308 (such as a controller), operablycoupled to the transceiver and arranged to collate and forward at leasta portion of dual connectivity terminal device status information to thesecond wireless access node upon at least one from a group of:establishment of a group of serving cells associated with the secondwireless access node (SeNB), receipt of updated dual connectivityterminal device status information from the dual connectivity terminaldevice.

Furthermore, in some examples, a wireless access node (such as a SeNB)is described for a wireless communication system that comprises a firstwireless access network and a second wireless access network supportinga dual connectivity terminal device arranged to communicate with both afirst wireless access node (such as a MeNB) on the first wireless accessnetwork and the wireless access node (such as the SeNB) on the secondwireless access network. In some examples, a cell group includes bothmacro cells and small cells. For example, a typical use case is that aMCG only comprises one or more macro cells whilst an SCG only comprisesone or more small cells.

The wireless access node (such as MeNB) comprises: a transceiver; aprocessor 308, operably coupled to the transceiver and arranged toreceive at least one from a group of: a portion of dual connectivityterminal device status information from the first wireless access node;dynamic configuration information concerning uplink transmissions to thesecond wireless access node from the dual connectivity terminal devicefollowing at least one from a group of: establishment of a group ofserving cells associated with the wireless access node, a change in dualconnectivity terminal device status information following at least onefrom a group of: establishment of a group of serving cells associatedwith the wireless access node, a change in dual connectivity terminaldevice status information.

Referring to FIG. 4, a simplified message sequence chart 400 for UEstatus forwarding is illustrated, comprising a UE 401, MeNB 403, SeNB405. In this example, modifications to existing message flows orsignaling may not introduce changes affecting UEs and UE statusreporting procedures, currently defined for the Uu interface. Further,in some examples, there is no change to UE status forwarding across theX2 interface, for example between eNBs during a handover procedure.However, in other examples, modifications to existing message flows orsignaling, such as semi-persistent scheduling as described with respectto FIG. 8 and FIG. 9, will introduce changes affecting UEs and signalsexchanged across the Uu interface, currently defined for the Uuinterface. Initially, in this example at 409, the UE 401 provides someor all of status information to the MeNB 403.

In accordance with some examples, the MeNB 403 decides to reconfigure,remove or add one or more secondary cells (Scells) to the SCG, therebyrequiring a change to the dual connectivity UE or providing dualconnectivity to the UE. At this point, the MeNB 403 forwards UE statusinformation, which was collected at 409, to the one or more SeNB(s) 405at 411. A large portion of the SCG configuration is assigned by the SeNB405, which is signaled to the UE via the MeNB 403. In some furtherexamples, the MeNB 403 forwards UE status information when initiatingreconfiguration procedure towards the SeNB 405 to add or modify one ormore SCell(s). In some examples, the MeNB 403 forwards UE statusinformation to the SeNB 405 within an X2 message that is usedspecifically for the transfer of this UE status information. In someexamples, the MeNB 403 forwards UE status information to the SeNB 405within an X2 message used to request the SeNB 405 to add or modify oneor more SCell(s) in order to establish a new SCG, for example request aninitiate SCG re-configuration. The message is sometimes referred to asSCG-Config, whereas in other scenarios the message is referred to as,for example, an SeNB addition or modification request, or the like Insome examples, it is envisaged that any acknowledgement (Ack) message islocated immediately following the SCG Config, whilst in other examplesit is contemplated that the Ack message be located at the end of themessage sequence chart, such as after a number of SCG-Config messages.In some examples, the X2 interface is assumed to use the same transportlayer protocol as S1 or X2, such as SCTP over IP for C-plane and GTP-Uover UDP or IP for U-plane.

In some examples, the UE 401 provides the MeNB 403 with updated(changed) status information at 413, for example if the UE 401 haschanged position within the network or upgraded its capabilities orservices, or the like. In response to receiving updated (changed) statusinformation at 413, the MeNB 403 updates its stored UE statusinformation and signals this to the SeNB 405 at 415. In some examples,the signaling at 415 to the SeNB 405 comprises a new X2 message orprocedure, transmitted over an X2 interface for example, introduced forthe transfer of UE status information. This may not include an MeNB 403command, nor any updated grant or restriction, configuration of UE 401capability.

In some examples, an unconfirmed flow (class 2) message is used whenonly forwarding UE status information, otherwise a confirmed flow(class 1) message is used. Alternatively, in some examples, a class ofmessage used depends on the initial message contents. In some examples,the updated status information 413 comprises one or more of, or a partof, InDeviceCoexlndication, UEAssistanceInformation orMBMSInterestIndication messages. In some examples, a separate messagespecifically used for this purpose such as a UE context transfer messageis sent at 415. In some examples, the forwarded UE status informationcomprises the full UE status information received from UE 401. In someother examples, the forwarded UE status information is a subset ofinformation received at 409, which is filtered based on the MeNB'sknowledge of the capabilities of the target SeNB 405. In other examples,the MeNB 403 is arranged to only transmit 415 updated or changedinformation to SeNB 405 that it determines to be relevant or beneficialto the SeNB 405.

Referring to FIG. 5, a simplified message sequence chart 500 of asecondary cell addition or modification procedure to a SCG isillustrated. The simplified message sequence chart 500 comprises UE 501,MeNB 503, SeNB 505, S-GW 507 and MME 509. Initially, at 511, a resourceradio manager (RRM) signals within the MeNB 503 determines whether toadd or modify resources of the SeNB 505. If it is determined that theresources of the SeNB 505 resources are to be added or modified, theMeNB 503 sends a command 513 to the SeNB 505 that it should add one ormore cell(s), and then the SeNB 505 decides the configuration of thatcell and sends this configuration information via MeNB 503 to the UE501. In some examples, the MeNB 503 forwards UE status informationwithin a message 515 requesting the SeNB 505 to configure one or moreSCells, for example a message 515 used to establish an SCG configurationin case of SCG establishment or addition. This has the advantage that noadditional messages need to be transferred to signal the UE statusinformation.

In some other examples, the UE status information is conveyed in aseparate message used specifically for UE status forwarding. Thismessage may, for example, is a UE specific class 2 X2 message orprocedure, for example specifically designed to transfer UE status orcontext information. This has an advantage of limiting standardschanges, as it would imply that for initial forwarding, the same messageas that used for a change of UE status information would be used. Insome examples, the MeNB 503 forwards the complete, or a subset of, UEstatus information to the SeNB 505. In some examples, the MeNB 503transfers UE status information to SeNB 505 via a SeNB addition ormodification request message 515 upon SCG establishment orre-configuration, as well as via, say, an additional, message upon UE501 status change, wherein the message is used specifically for UEstatus forwarding.

At 517, the SeNB 505 may, after receiving the forwarded RRM decision,admit resources and allocate L1 and L2 resource. Further, the SeNB 505provides a dedicated RACH configuration to the dual connectivity UE 501for synchronization purposes. At 519, the SeNB 505 transmits an additionmodification command to the MeNB 503, thereby enabling the MeNB 503 totransmit an RRC ConnectionReconfiguraton message 521 to the dualconnectivity UE 501. Subsequently, the MeNB 503 initiates an SN statustransfer at 523 and thereafter performs data forwarding at 525. Once thedual connectivity UE 501 has reconfigured its connection, it transmitsan RRC ConnectionReconfigurationComplete message 527 to the MeNB 503,before performing a random access procedure 529 with the SeNB 505.

Once the random access procedure 529 from the dual connectivity UE 501to the SeNB 505 has been initiated, the SeNB 505 transmits an additionor modification complete message 531 to the MeNB 503. In response toaddition or modification complete message 531, the MeNB 503 transmits anE-RAB modification indication message 533 to MME 509, wherein the MME509 subsequently transmits a bearer modification command 535 to S-GW 507and subsequently transmits an E-RAB modification confirmation 537 toMeNB 503.

Referring to Table. 1, changes to message contents of the SCGestablishment or addition message, referred to as, for example, the SCGcommand, or an SeNB addition or modification request, or the like, areillustrated, in the direction from the MeNB 503 to the SeNB 505.

TABLE 1 Item Field Presence Description Notes 1 Message type M 2 UE Id MSome kind of UE No change identification 3 UE capability M/O Used tocoordinate No change the split of UE capabilities between MCG and SCG 4UE AS O Used to coordinate No change configuration the split of UEcapabilities between MCG and SCG 5 UE context O Used to transfer UEIncludes the information context information, UE status information

Referring to Table. 2, changes to UE context message contents areillustrated, in the direction of the MeNB 503 to the SeNB 505.

TABLE 2 Item Field Presence Description Notes 1 Message type M 2 UE Id MSome kind of UE As for any identification UE specific message 5 UEcontext M Used to transfer UE Includes the information contextinformation, UE status information

Referring to FIG. 6, a block diagram of wireless communication units,for example UE 225 and SeNB 203, adapted in accordance with some exampleembodiments of this disclosure, are shown. The wireless communicationunits 225, 203 comprise similar features to the wireless communicationunits illustrated in FIG. 3. Therefore, only additional functionalitywill be described relating to FIG. 6.

In FIG. 6, the wireless communication system again comprises a firstwireless access network and a second wireless access network, whereby adual connectivity terminal device, such as dual connectivity UE 225, isarranged to communicate with both a wireless access node (such as a MeNB210) on the first wireless access network and a second wireless accessnode (such as a SeNB 203) on the second wireless access network. Thewireless communication units 225 contains an antenna 602, for receivingtransmissions, coupled to an antenna switch or duplexer 604 thatprovides isolation between receive and transmit chains within thewireless communication units. One or more receiver chains, as known inthe art, include receiver front-end circuitry 606 (effectively providingreception, filtering and intermediate or base-band frequencyconversion). The receiver front-end circuitry 606 is coupled to a signalprocessing module 608 (generally realized by a digital signal processor(DSP)). A skilled artisan will appreciate that the level of integrationof receiver circuits or components is, in some instances,implementation-dependent.

The controller 614 maintains overall operational control of the wirelesscommunication unit 225. The controller 614 is also coupled to thereceiver front-end circuitry 606 and the signal processing module 608.In some examples, the controller 614 is also coupled to a buffer module617 and a memory device 616 that selectively stores operating regimes,such as decoding or encoding functions, synchronization patterns, codesequences, and the like. A timer 618 is operably coupled to thecontroller 614 to control the timing of operations (such as transmissionor reception of time-dependent signals) within the wirelesscommunication unit 225. As regards the transmit chain, this essentiallyincludes an input module 620, coupled in series through transmitter ormodulation circuitry 622 and a power amplifier 624 to the antenna 602,antenna array, or plurality of antennas. The transmitter or modulationcircuitry 622 and the power amplifier 624 are operationally responsiveto the controller 614.

The dual connectivity terminal device, comprises a transceiver and aprocessor 608, operably coupled to the transceiver and arranged toprovide status information concerning uplink transmissions to the secondwireless access node (such as the SeNB 203) operating on the secondwireless access network.

In some examples, the processor 608 is arranged to provide (dynamic)status information concerning uplink transmissions to the secondwireless access node, such as SeNB 203, in response to a change of thestatus information previously provided to the second wireless accessnode, such as SeNB 203, or provided initially upon establishment of asecondary cell group (SCG). As has been discussed above, there are caseswhere a UE has insufficient power to handle all uplink transmissions. Insome examples, in order to address this problem, the dual connectivityUE 225 is operable to forward or update the SeNB 203 with MeNB relatedUL scheduling information.

Therefore, and referring to FIG. 7, a sequence chart 700 illustrates anexample of uplink data in a PCell and pSCell is illustrated comprising,PUSCH voice data 701 and PUSCH high bit rate packet service 703. Aspreviously mentioned, uplink power limitations are encountered due to adual connectivity UE being scheduled by to communicate with both thePCell and pSCell at the same time, with both eNBs in the PCell andpSCell attempting to fully utilize any spare power headroom. It isconsidered generally that PHR reports reflect the current UL powersituation and thus have limited value with respect to predicting thefuture UL power situation. That is, if the PHR report indicates that theUE has an UL power limitation or shortage, this does not necessarilymean that the UE will be power limited in the near future, as the needto transmit uplink data rate changes as well as the power required totransmit a certain data rate (due to radio link quality changes).

Therefore, in accordance with some examples, it is advantageous toprovide the SeNB with dynamic UE configuration information concerningsemi-persistent resource allocations by the MeNB, such as uplink (UL)periodic transmissions that are currently configured at the UE. It isnoted that the persistent allocations are handled by the normalsemi-static configuration that E-UTRAN assigns to the UE, while theinformation in this example concerns more dynamic information, forexample concerning activation of semi-persistent resource allocations,which is not exchanged by RRC but by lower layers which is quicker.Therefore, in some examples, the semi-static configuration informationprovided to the SeNB covers both PUCCH and PUSCH transmissions from UEto MeNB, and includes at least one of semi-persistent scheduling (SPS)configuration, channel state information (CSI) and sounding referencesymbol (SRS) configuration, PRACH configuration and scheduling requestconfiguration.

In some examples, a typical use case is that voice would be transferredvia a master cell group (MCG), whilst most other traffic is exchangedvia a SCG. To support some more dynamicity with SPS (taking into accountthat voice is typically bursty in nature), a mechanism has been definedfor activating or deactivating the SPS configuration using downlinkcontrol information at the physical layer. In other examples, a typicalcase is for the MeNB to provide this kind of more dynamic informationconcerning semi-persistent or periodic UL transmissions to the SeNB toavoid UL power limitations. In this manner, the MeNB schedules the UEsuch that, in SCG cells, no UL transmissions collide with thesesemi-persistent or periodic MCG UL transmissions. In other examples, theUE provides this more dynamic (SPS activation) information to the SeNB,for example using medium access control (MAC) signaling. After beinginformed of the activation status, the SeNB is able to avoid schedulingthe UE at those MeNB allocated occasions and only when SPS is reallyactivated (such as during the actual speech burst, but not during thesilence period in-between).

In some examples, it is advantageous for a master eNB to provide uplinkSPS activation status information, for a particular UE, to a relevantsecondary eNB, as described below with respect to FIG. 8 and FIG. 9.Referring to FIG. 8, a simplified high level message sequence for uplinkSPS activation status 800 is shown. The simplified high level messagesequence chart 800 illustrates communications between dual connectivityUE 801, MeNB 803 and SeNB 805. Initially, the MeNB 803 and the dualconnectivity UE 801 employ a RRC re-configuration process, say via RRCConnectionReconfiguration messages 807, which in this example comprisesthe MeNB 803 configuring the dual connectivity UE 801 with uplinksemi-persistent scheduling (SPS). For example, the MeNB 803 assigns anuplink SPS-configuration, signaled by means of theRRCConnectionReconfiguration message, which includes a patternspecifying periodically repeating uplink scheduling opportunitiesassigned to dual connectivity UE 801.

Subsequently, the MeNB 803 transmits message 809 to the dualconnectivity UE 801, in order to activate the uplink SPS configuration,say via a physical downlink control channel (PDCCH) (Layer 1) SPSactivation message. It should be noted that although only one PDCCHmessage 809 is illustrated in FIG. 8, it is likely that the MeNB 803regularly or periodically uses activation or deactivation upon everyspeech burst illustrated, for example as described with respect to FIG.7. Subsequent to the E-UTRAN (or MeNB 803) adding or configuring orre-configuring a secondary cell group (SCG) comprising one or moreSCells controlled by SeNB 805, the UE 801 provides the uplink SPSactivation status information to the SeNB 805 via message 813. At sometime thereafter, MeNB 1003 will send a further PDCCH (Layer 1) SPSdeactivation message to the UE 801 in message 815.

Advantageously, as part of this procedure, the MeNB 803 provides theuplink SPS activation status information to the SeNB 805 via message813, as well as utilizing the information provided by the E-UTRAN toactivate uplink SPS configuration in the dual connectivity UE 801 viamessage 809. In some examples, message 813 includes a start time, thatrelates to subframe timing of 809 transmission. Further, andadvantageously, the MeNB 803 subsequently signals, via uplink SPSactivation status message 817, updated or changed uplink SPS activationstatus information to the SeNB 805.

In some examples, after the MeNB 803 transmits SPS deactivation message809 to dual connectivity UE 801, the MeNB 803 subsequently signals acomplete dual connectivity UE configuration to the SeNB 805, withoutincluding SPS configuration information. In some other examples, theMeNB 803 or the dual connectivity UE signals a dual connectivity UE'suplink SPS activation status to the SeNB 805 by utilising an ‘on’ or‘off’ indication, which in some examples includes a specific start-timeand an activation status indicator or flag reflecting the ‘on’ or ‘off’activation status. Note that, in some examples, the semi-static SPSconfiguration only includes the interval between the subsequent periodicallocations, as the start time is derived from the sub-frame timing inwhich the UE receives the SPS activation command via a PDCCH (L1).Hence, the start time is dynamic also, and is provided to the SeNB uponevery SPS activation.

Referring to Table. 3 below, the contents of the SCG command message(sometimes also referred to as SeNB addition or modification request)contents are illustrated, in the direction of the MeNB 803 to the SeNB805.

TABLE 3 Item Field Presence Description Notes 1 Message type M 2 UE Id MSome kind of UE No change identification 3 UE M/O Used to coordinate Nochange capability the split of UE capabilities between MCG and SCG 4 UEAS O Used to coordinate No change configuration the split of UEcapabilities between MCG and SCG 5 UE As O Used to transfer UE Includesthe configuration, context information, UL SPS dynamic part activationstatus information

Referring to Table. 4, the contents of the UE context indication messagecontents are illustrated, in the direction of the MeNB 803 to the SeNB805.

TABLE 4 Item Field Presence Description Notes 1 Message type M 2 UE Id MSome kind of UE As for any identification UE specific message 3 UE As OUsed to transfer UE Includes the configuration, context information, ULSPS dynamic part activation status information

Referring to FIG. 9, a high level message sequence chart 900 illustratesa case where the UE provides this more dynamic configuration informationconcerning semi-persistent or periodic UL allocations to the SeNB. Thehigh level message sequence chart 900 illustrates communications betweenUE 901, MeNB 903 and SeNB 905. In this example, the MeNB 903 and UE 901employs a RRC re-configuration process, say via RRCConnectionReconfiguration messages 907, which in this example comprisesthe MeNB 903 assigning an uplink SPS-Config including a patternspecifying periodically repeating uplink scheduling opportunitiesassigned to UE 901.

Subsequently, the MeNB 903 transmits message 909 to the UE 901, in orderto activate the uplink SPS configuration, via a physical downlinkcontrol channel (PDCCH) (Layer 1) SPS activation message. It should benoted that although only one PDCCH message 909 is illustrated in FIG. 9,it is likely that the MeNB 903 regularly or periodically sendsactivation or deactivation messages to a number of dual connectivity UEsupon every speech burst illustrated, for example as illustrated withrespect to FIG. 8. Subsequent to the E-UTRAN (or MeNB 903) adding orconfiguring or re-configuring a secondary cell group (SCG) comprisingone or more SCells controlled by SeNB 905, the UE 901 provides theuplink SPS activation status information to the SeNB 905 via message913. At some time thereafter, MeNB 903 will send a further PDCCH(Layer 1) SPS deactivation message to the UE 901 in message 915. In someexamples, the UE 901 informs the SeNB 905 about the uplink activationstatus in message 917 by means of a new medium access control (MAC)control element (CE), as illustrated in FIG. 10.

Further, and advantageously, the UE 901 subsequently signals, via uplinkSPS activation status message 917, updated (changed) uplink SPSactivation status information to the SeNB 905. In some examples, theoperation of the SeNB 905 upon receiving the activation or de-activationindication from the dual connectivity UE 901, is the same as whenreceiving the information from the MeNB 903.

In this manner, in accordance with some examples and possibly ratherthan fixing operational parameters such as power headroom of the dualconnectivity UE 901 using power headroom reporting (PHR), when the dualconnectivity UE 901 is configured to communicate with an SCG, the SeNB905 is provided with information regarding semi-static periodic ULtransmissions of the dual connectivity UE 901 towards the MeNB. In thismanner, the SeNB is able to schedule UL resources with UE 901 that donot collide with UL resources being taken by communications between thedual connectivity UE 901 and MeNB 903.

In some examples, the PHR reporting is also intended to affect thescheduling such as to avoid that scenario a UE is allocated a lot ofresources whilst it has insufficient power for the concerned uplinktransmissions in MCG and SCG. Therefore, in some examples, it ispossible to avoid sending PHR changes to effect the same result. In someexamples, however, it is envisaged that the concepts herein describedalso is used in combination with an enhanced PHR reporting scheme.

Referring to FIG. 10, an activation or deactivation MAC control element(CE) 1000 is illustrated in accordance with some example embodiments ofthis disclosure. In this example, the MAC CE 1000 comprises a single ‘C’bit 1002 indicating the activation status of UL SPS activation in thePCell. In some examples, more bits than just the single ‘C’ bit isintroduced to cover future UL SPS that are configured for other mastercell groups (MCG), or where there are multiple SCGs. Furthermore, theMAC CE 1000 includes two fields indicating the start time 1004 of theSPS allocations, a first part indicating an SFN offset and a second partindicating the actual sub-frame 1006 within the radio frame indicated bythe SFN offset. The SFN offset does not need to employ the full SFNrange, as it defines a frame that is relative to timing used for thetransfer of the MAC CE 1000. The figure merely shows a possible exampleof the actual signalling such as that the number of bits are different,while the sub-frame timing is represented by a single field. The figureillustrates also merely one possible example regarding the use ofreserved bits.

Referring to FIG. 11, a message sequence chart for control ofsemi-persistent scheduling is illustrated. As shown, dual connectivityoperation is illustrated, comprising UE 1101, macro cell MeNB 1103 andsmall-cell SeNB 1105. As illustrated, all SPS activation anddeactivation messages are controlled by macro cell eNB 1103. Initially,at 1111, the MeNB 1103 decides to add a secondary cell, such as a smallcell to an existing secondary cell group, such as a secondary cellgroup. At 1113, a request is then sent from the MeNB 1103 to the SeNB1105 to establish a secondary cell group. The request includes thecurrent dedicated radio resource configuration assigned by the MeNB suchas covering the configuration related to the master cell group. Thisdedicated radio resource configuration includes Physical Uplink ControlChannel (PUCCH) configuration physical random access channel (PRACH)configuration and SPS configuration of the primary serving cell (PCell).A response is then sent from the SeNB 1105 at 1115 including theconfiguration related to the secondary cell group, which the MeNBforwards to the UE. This secondary cell group configuration includes,inter alia, the PUCCH configuration of the pSCell. The SeNB usesdedicated resource configuration received from the MeNB when configuringthe pSCell PUCCH such that it does not collide with PCell channel stateinformation (CSI) or sounding reference signals (SRS) in the timedomain. The MeNB 1103 then informs the UE 1101 that the SeNB 1105 hasbeen added to the secondary (small cell) cell group at 1117. The UE isthen able to access the SeNB by sending a Random Access CHannel (RACH)request at 1119. Thereafter, the UE 1101 is able to operate with dualconnectivity with both MeNB 1103 at 1121 and SeNB 1105 at 1123.

The SeNB 1105 then schedules Physical Uplink Shared Channel (PUSCH),such that it does not collide with the PCell's CSI or SRS at 1125. TheMeNB 1103 then changes the PUCCH configuration at 1127 and inform theSeNB 1105 of the updated PUCCH configuration at 1129. At this point, theSeNB 1105 decides to re-configure the pSCell PUCCH such that it does notcollide in the time domain with the PCell CSI or SRS. The re-configuredpSCell PUCCH information then is sent to the MeNB 1103 at 1131 and theUE at 1133.

At some later time, the MeNB 1103 decides to activate uplinksemi-persistent scheduling (UL SPS) at 1135. The MeNB 1103 theninstructs the UE 1101 to activate UL SPS at 1137. According to currentstate of the art, the SeNB is, however, neither aware of the activationstatus of SPS nor of the precise starting time of the periodic SPSresource allocations. Hence, it is currently not able to schedule PUSCHtransmissions such that they do not collide with any UL SPStransmissions in the Master Cell Group. At some later time, the MeNB1103 decides to deactivate UL SPS at 1140. The MeNB 1103 then instructsthe UE 1101 to deactivate UL SPS at 1143.

Referring to FIG. 12, a modified message sequence chart 1200 for controlof semi-persistent scheduling is illustrated. The first section 1209refers to the first part of FIG. 11 and, therefore, no furtherexplanation of the first section will be given. The second section 1250refers to a new and advantageous X2 co-ordination and UE reportingphase. Initially, the X2 coordination and UE reporting phase commenceswith static information being exchanged between UE 1201, MeNB 1203 andSeNB 1205 over an X2 interface.

In accordance with example embodiments, dynamic configurationinformation, for example SPS activation or deactivation messages isreported by UE 1201 directly to SeNB 1205, via a new medium accesscontrol (MAC) layer control element (CE) 1252. In some examples, forexample when employing a new MAC CE 1252, the UE 1201 triggers a new MACCE when a defined uplink transmission with some periodicity, for examplevoice over internet protocol (VoIP), is utilised. The MAC CE 1252includes pattern information of the regular uplink transmission, forexample the starting point of time.

In some other examples, for example when reusing one or more PHR MAC CEs1254, the UE 1201 triggers the PHR MAC CE when a defined uplinktransmission with some periodicity, for example VoIP, is utilised. Inthis example, two PHR MAC CEs is transmitted in a MAC PDU. The first PHRcomprises PHs for communications with SeNB 1205, and the second PHRcomprises PHs for communications with MeNB 1203. Similarly, in someexamples, the UE 1201 receives, for example, an SPS deactivation message1256 from MeNB 1203. In response to this message, the UE 1201 eithertriggers a new MAC CE 1258 or two PHR MAC CEs in a MAC PDU 1260.

In particular, it is envisaged that the aforementioned inventive conceptis applied by a semiconductor manufacturer to any integrated circuitcomprising a signal processor configured to perform any of theaforementioned operations. Furthermore, the inventive concept is appliedto any circuit that is able to configure, process, encode, or decodesignals for wireless distribution. It is further envisaged that, forexample, a semiconductor manufacturer employs the inventive concept in adesign of a stand-alone device, such as a digital signal processor, orapplication-specific integrated circuit (ASIC) or any other sub-systemelement.

It will be appreciated that, for clarity purposes, the above descriptionhas described embodiments of this disclosure with reference to differentfunctional units and processors. However, it will be apparent that anysuitable distribution of functionality between different functionalunits or processors, for example with respect to the signal processor308, 608, is used without detracting from this disclosure. For example,functionality illustrated to be performed by separate processors orcontrollers is performed by the same processor or controller. Hence,references to specific functional units are only to be seen asreferences to suitable means for providing the described functionality,rather than indicative of a strict logical or physical structure ororganization.

Aspects of this disclosure are implemented in any suitable formincluding hardware, software, firmware or any combination of these. Thisdisclosure optionally can be implemented, at least partly, as computersoftware running on one or more data processors or digital signalprocessors or configurable module components such as FPGA devices. Thus,the elements and components of an embodiment of this disclosure isphysically, functionally and logically implemented in any suitable way.Indeed, the functionality is implemented in a single unit, in aplurality of units or as part of other functional units.

Although the present invention has been described in connection withsome embodiments, it is not intended to be limited to the specific formset forth herein. Rather, the scope of the present invention is limitedonly by the accompanying claims. Additionally, although a featureappears to be described in connection with particular embodiments, oneskilled in the art would recognize that various features of thedescribed embodiments is combined in accordance with this disclosure. Inthe claims, the term ‘comprising’ does not exclude the presence of otherelements or steps.

Furthermore, although individually listed, a plurality of means,elements or method steps are implemented by, for example, a single unitor processor. Additionally, although individual features are included indifferent claims, these arepossibly advantageously combined, and theinclusion in different claims does not imply that a combination offeatures is not feasible or advantageous. Also, the inclusion of afeature in one category of claims does not imply a limitation to thiscategory, but rather indicates that the feature is equally applicable toother claim categories, as appropriate.

Thus, communication units such as wireless access nodes and terminaldevices, a communication system and methods relating to implementingdual connectivity for terminal devices such as UEs have been described,wherein the aforementioned disadvantages with prior art arrangementshave been substantially alleviated.

Although the present disclosure has been described with an exemplaryembodiment, various changes and modifications is suggested to oneskilled in the art. It is intended that the present disclosure encompasssuch changes and modifications as fall within the scope of the appendedclaims.

What is claimed is:
 1. A method by a first base station in a wirelesscommunication system supporting a dual connectivity, the methodcomprising: transmitting, to a second base station, a first messageincluding configuration information for a secondary cell group (SCG),the first message being used to request the second base station toperform a certain action related to configuration of the SCG; receiving,from the second base station, a second message in response to the firstmessage, the second message being associated with the certain action;and transmitting, to a terminal, a third message based on the secondmessage, wherein the configuration information includes multimediabroadcast multicast service (MBMS) interest information and in devicecoexistence (IDC) information for the terminal, and wherein the MBMSinterest information is used to inform that the terminal is interestedto receive MBMS via a multicast radio bearer (MRB) and the IDCinformation is related to interference by multiple radio transceiverswithin the terminal.
 2. The method of claim 1, wherein the MBMS interestinformation is further used to inform that the terminal is no longerinterested to receive the MBMS via the MRB.
 3. The method of claim 1,wherein the first message is transmitted to the second base stationusing an X2 message.
 4. The method of claim 1, wherein the first messageis at least one of an addition request message and a modificationrequest message.
 5. The method of claim 1, wherein the third messagecomprises a radio resource control (RRC) connection reconfigurationmessage.
 6. The method of claim 1, wherein the certain action includesat least one of establishment and modification of the SCG.
 7. A methodby a second base station in a wireless communication system supporting adual connectivity, the method comprising: receiving, from a first basestation, a first message including configuration information for asecondary cell group (SCG), the first message being used to request thesecond base station to perform a certain action related to configurationof the SCG; and transmitting, to the first base station, a secondmessage in response to the first message, the second message beingassociated with the certain action, wherein the configurationinformation includes multimedia broadcast multicast service (MBMS)interest information and in device coexistence (IDC) information for aterminal, and wherein the MBMS interest information is used to informthat the terminal is interested to receive MBMS via a multicast radiobearer (MRB) and the IDC information is related to interference bymultiple radio transceivers within the terminal.
 8. The method of claim7, further comprising: admitting resources and allocating layer 1 (L1)and layer 2 (L2) resources in response to the received first message. 9.The method of claim 7, wherein the MBMS interest information is furtherused to inform that the terminal is no longer interested to receive theMBMS via the MRB.
 10. The method of claim 7, wherein the first messageis transmitted to the second base station using an X2 message.
 11. Themethod of claim 7, wherein the first message is transmitted to thesecond base station using an addition request message and a modificationrequest message.
 12. The method of claim 7, wherein the certain actionincludes at least one of establishment and modification of the SCG. 13.A first base station in a wireless communication system supporting adual connectivity, the first base station comprising: a transceiver; anda controller coupled with the transceiver and configured to control to:transmit, to a second base station, a first message includingconfiguration information for a secondary cell group (SCG), the firstmessage being used to request the second base station to perform acertain action related to configuration of the SCG, receive a secondmessage in response to the first message from the second base station,the second message being associated with the certain action, andtransmit a third message based on the second message to a terminal,wherein the configuration information includes multimedia broadcastmulticast service (MBMS) interest information and in device coexistenceinformation (IDC) for the terminal, and wherein the MBMS interestinformation is used to inform that the terminal is interested to receiveMBMS via a multicast radio bearer (MRB) and the DC information isrelated to interference by multiple radio transceivers within theterminal.
 14. The first base station of claim 13, wherein the MBMSinterest information is further used to inform that the terminal is nolonger interested to receive the MBMS via the MRB.
 15. The first basestation of claim 13, wherein the first message is transmitted to thesecond base station using an X2 message.
 16. The first base station ofclaim 13, wherein the first message is transmitted to the second basestation using an addition request message and a modification requestmessage.
 17. The first base station of claim 13, wherein the thirdmessage comprises a radio resource control (RRC) connectionreconfiguration message.
 18. The first base station of claim 13, whereinthe certain action includes at least one of establishment andmodification of the SCG.
 19. A second base station in a wirelesscommunication system supporting a dual connectivity, the second basestation comprising: a transceiver; and a controller coupled with thetransceiver and configured to control to: receive, from a first basestation, a first message including configuration information for asecondary cell group (SCG), the first message being used to request thesecond base station to perform a certain action related to configurationof the SCG, and transmit a second message in response to the firstmessage to the first base station, the second message being associatedwith the certain action, wherein the configuration information includesmultimedia broadcast multicast service (MBMS) interest information andin device coexistence (IDC) information for a terminal, and wherein theMBMS interest information is used to inform that the terminal isinterested to receive MBMS via a multicast radio bearer (MRB) and theIDC information is related to interference by multiple radiotransceivers within the terminal.
 20. The second base station of claim19, wherein the controller further configured to admit resources and toallocate layer 1 (L1) and layer 2 (L2) resources in response to thereceived first message.
 21. The second base station of claim 19, whereinthe MBMS interest information is further used to inform that theterminal is no longer interested to receive the MBMS via the MRB. 22.The second base station of claim 19, wherein the first message istransmitted to the second base station using an X2 message.
 23. Thesecond base station of claim 19, wherein the first message istransmitted to the second base station using an addition request messageand a modification request message.
 24. The second base station of claim19, wherein the certain action includes at least one of establishmentand modification of the SCG.